Skip to content

Fixes TPU detection logic#77

Merged
divyashreepathihalli merged 1 commit intomainfrom
gke-fix
Mar 8, 2026
Merged

Fixes TPU detection logic#77
divyashreepathihalli merged 1 commit intomainfrom
gke-fix

Conversation

@JyotinderSingh
Copy link
Collaborator

Issue

The decorator was still failing to detect a few node pool types, even after #75.

Fix

Infers accelerator count from machine type using registry. This is robust because it uses the same source of truth as the Pod spec generation.

Tested this with multiple pod types internally, and it works.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves an issue where the system failed to correctly identify certain TPU node pool types. The solution involves a more robust method of determining the accelerator count by referencing a machine type registry, ensuring consistency with Pod specification generation and improving the overall reliability of TPU detection.

Highlights

  • Improved TPU Detection Logic: The pull request enhances the TPU detection logic by inferring the accelerator count directly from the machine type using an internal registry. This approach ensures robustness by aligning with the same source of truth used for Pod spec generation, addressing previous failures in detecting certain node pool types.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • keras_remote/backend/gke_client.py
    • Implemented logic to infer the accelerator count for TPUs based on the machine type, using a predefined registry.
Activity
  • No human activity has occurred on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@JyotinderSingh JyotinderSingh requested a review from jeffcarp March 7, 2026 06:07
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request fixes an issue with TPU detection by inferring the accelerator count from the machine type, which is a robust approach. I've left one comment with a suggestion to improve the efficiency of the added loop.

Comment on lines +466 to +470
for tpu_spec in accelerators.TPUS.values():
for chips, topo_spec in tpu_spec.topologies.items():
if topo_spec.machine_type == machine_type:
pool_labels["cloud.google.com/gke-accelerator-count"] = str(chips)
break
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The break on line 470 only exits the inner loop. The outer loop continues to iterate through the remaining tpu_specs even after a match is found, which is inefficient. You can use a for...else construct to break out of both loops once a match is found.

Suggested change
for tpu_spec in accelerators.TPUS.values():
for chips, topo_spec in tpu_spec.topologies.items():
if topo_spec.machine_type == machine_type:
pool_labels["cloud.google.com/gke-accelerator-count"] = str(chips)
break
for tpu_spec in accelerators.TPUS.values():
for chips, topo_spec in tpu_spec.topologies.items():
if topo_spec.machine_type == machine_type:
pool_labels["cloud.google.com/gke-accelerator-count"] = str(chips)
break
else:
continue
break

@divyashreepathihalli divyashreepathihalli merged commit ef4b74d into main Mar 8, 2026
4 checks passed
@JyotinderSingh JyotinderSingh deleted the gke-fix branch March 8, 2026 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants